Scalable communication system, method and apparatus

ABSTRACT

A method of sharing a satellite communication system having a common equipment includes billing a first user for sending a first message using the common equipment over a first satellite link, billing a second user for sending a second message using the common equipment over a second satellite link, wherein the first satellite link is different than the second satellite link, billing a first network operator for billing the first user, and billing a second network operator for billing the second user.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a divisional of U.S. patent application Ser.No. 11/012,270, filed Dec. 16, 2004, which claims priority to U.S.provisional patent application Ser. No. 60/530,264, filed Dec. 18, 2003,and U.S. provisional patent application Ser. No. 60/543,537, filed Feb.12, 2004, and contains subject matter related to that disclosed incommonly owned U.S. patent application Ser. No. 11/012,256, filed Dec.16, 2004, U.S. patent application Ser. No. 11/012,343, filed Dec. 16,2004, U.S. patent application Ser. No. 11/012,269, filed Dec. 16, 2004,and U.S. patent application Ser. No. 11/012,359, filed Dec. 16, 2004,the entire contents of each of which being incorporated herein byreference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to communication networks and moreparticularly to a communication system including shared, independentlymanaged communication networks. The present invention also relates to amethod of providing shared independently managed communication networks,and to an apparatus in a shared independently administered network.Further, the present invention relates to communication networks thatare satellite communication networks.

2. Discussion of the Background

A conventional satellite network communication system business methodincludes a satellite network provider and satellite network users. Thesatellite network provider obtains all the equipment, includingteleport, remote equipment and related software, and providescommunication network services to network users for a fee.

FIG. 16 shows an example of a conventional satellite networkcommunication system including network upstream users 1602 and networkremote users 1612 that communicate via Internet Protocol (IP) network1604, teleport 1606, satellite IF/RF converter 1608 and satellite 1610.Further, a network operator 1614 performs network management functions.A teleport 1606 provides a connection between an IP network and a singleIF/RF converter 1608 with a connection to a single satellite 1610.

FIG. 17A shows an example of the composition of teleport 1606, includingprocessor 1702 and dedicated hub modem chassis 1706.

FIG. 17B shows another example of a background teleport 1700 that issimilar to teleport 1606. However, background teleport 1700 includesconnections to two satellite IF/RF converters connected to two differentsatellites. Teleport 1700 includes processor A 1702 connected to an IPnetwork, processor B 1704 connected to an IP network, a dedicated hubmodem chassis A 1706, and a dedicated hub modem chassis B 1708.Dedicated hub modem chassis A 1706 provides an intermediate frequency(IF) connection to the satellite A IF/RF converter, which in turnconnects via a radio frequency (RF) path to satellite A (not shown), anddedicated hub modem chassis B 1708 provides an IF connection to thesatellite B IF/RF converter, which in turn connects via a RF path tosatellite B (not shown).

Thus, in this system a dedicated hub modem chassis is required for eachsatellite in a teleport, and each dedicated hub modem chassis canprovide a connection to only a single satellite, via a satellite IF/RFconverter. As recognized by the present inventors, additional expensesare unnecessarily incurred when more than one satellite network is to beoperated at a teleport. In addition, the addition of a new networknecessitates installation and administration of an additional teleportor an additional hub chassis for the new network. Thus, considerableplanning and expense are incurred when adding a new network.

FIG. 18 shows an example of a conventional method of operating asatellite communications network. When a new independently managednetwork is required, a new hub modem chassis must be added to ateleport, as shown in step S1802. In addition, a new satellite IF/RFconverter and a new satellite must be added to the communication system,as shown in step S1804. Next, the method includes adding upstream andremote users, as shown in step S1806, and operating the network, asshown in step S1808.

As recognized by the present inventors, it is difficult to incrementallyadd capabilities for new users. For example, to create a newindependently managed private satellite network, a satellite systemprovider must obtain, install, configure and manage at least anadditional hub modem chassis and line cards for the additional hub modemchassis.

Also, it is difficult to increase or decrease the amount of bandwidthallocated to a particular network. To increase the number of carriersallocated to a particular network (i.e., upstream) or adding a newnetwork (i.e., modem group and associated equipment for a network) inthe background art, it is necessary to add a teleport or add anadditional hub modem chassis, thereby incurring significant capitalexpense.

An alternative background approach is to combine a plurality of smallercustomers on a single network, and varying the amount of bandwidthallocated to each customer on that network as required. However, in thatalternative approach each network user does not have control over keynetwork parameters like IP address assignment, QoS, number of upstreams,and frame lengths. Further, security (e.g., password scheme, level ofencryption (at least up to Layer 3)) options are the same for allsatellite network system users in the background approach.

Further, this alternative background approach does not allow each userto customize the single network for their particular application (e.g.,VoIP, web browsing, shared database, etc . . . ). Thus, customers arenot able to independently take advantage of all network features and arerequired to coordinate the control of those features with a third partynetwork operator, thereby increasing expense and reducing customerflexibility and autonomy. Alternatively, to get flexible control overthese network parameters, each user of the background approach woulddisadvantageously need to spend additional money to set up independentnetworks dedicated to their application and tailored to their needs.

Further, this conventional satellite communication network includes alarge number of interrelated configuration parameters. The configurationparameters are interrelated because changes to parameters in one part ofthe communication network has an impact on another part, and may requirefurther changes to that other part of the network. A background methodof configuring a satellite communication network includes changing eachof the parameters one at a time from a network operator workstation andafter the final parameter is changed, waiting until the systemstabilizes to see if the changed parameters had the desired effect. Forexample, to change an IP address of a remote user in a backgroundsystem, a network operator enters the new IP address in the remote usersoftware, and then enters the new IP address in each related computerthat communicates with the remote user's IP address. Then, after thefinal IP address is changed, the operator waits to see if the change hadthe desired effect.

The present inventors recognized that a problem with this method ofconfiguring a satellite communication network is that as configurationparameters are changed, those changes may cause undesirable temporaryeffects in the communication network. Further, those effects may ripplethrough the communication network, causing problems that are moredifficult to repair. For example, when changing the IP address in theexample shown above, after changing the IP address on the remote usersoftware, a remote user loses the ability to communicate on the IPnetwork, and may start a communication recovery action that may includesending messages to a domain name server for example, or may includeother error recovery attempts that in turn may result in other errorsthat must be corrected. Consequently, operation of such a communicationsystem may be disadvantageously disrupted during a change ofconfiguration.

In addition, each user of a satellite network system shares a single IPaddress space. For example, if multiple independent users on a singlenetwork have network equipment with the same IP addresses, in thisconventional system, those independent users are required to changetheir IP addresses in a coordinated manner to ensure that no two deviceshave the same IP address. Thus, users of the background satellitenetwork system do not have a mechanism for independently defining IPaddresses to allow independent assignment of IP addresses that may bethe same, if multiple users each want some equipment to have the same IPaddress.

Moreover, this conventional system must coordinate with customer to makechanges to remotes because the system does not provide a mechanism fornetwork operators to easily make changes themselves without remote userinvolvement.

In addition, because configuration changes are made one remote at atime, configuration changes are time consuming and may disadvantageouslytake a long time to complete.

SUMMARY OF THE INVENTION

Accordingly, one object of the invention is to provide a novel scalablecommunication system, method, computer program product, and apparatuses.An embodiment of the communication system, method, computer programproduct, and apparatus includes common equipment shared between multipleindependently administered networks. The common equipment isreconfigurable and expandable and provides changed communicationcapacity and functions when additional elements are added orreconfigured. Configurable features include, for example, communicationbandwidth, Quality of Service, and a number of communication satellitesincluded in the communication system. The common equipment includesexpandable elements including, for example, a single hub modem chassisthat can expand to communicate with more than one communicationsatellite and a protocol processor that can share a protocol processingtask with another protocol processors.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete appreciation of the invention and many of the attendantadvantages thereof will be readily obtained as the same becomes betterunderstood by reference to the following detailed description whenconsidered in connection with the accompanying drawings, wherein:

FIG. 1 is a block diagram of a communication system according to anembodiment of present invention;

FIG. 2 is a block diagram of a communication system according to anotherembodiment of the present invention;

FIG. 3 is a block diagram of a communication system according to anotherembodiment of the present invention;

FIG. 4 is a block diagram of a shared multiport according to anembodiment of the present invention;

FIG. 5A is a block diagram of a shared multiport according to anotherembodiment of the present invention;

FIG. 5B is a block diagram of a shared multiport according to anotherembodiment of the present invention;

FIG. 5C is a block diagram of a shared multiport according to anotherembodiment of the present invention;

FIG. 6 is a block diagram of a shared hub modem chassis according to anembodiment of the present invention;

FIG. 7 is a block diagram of a modem group according to an embodiment ofthe present invention;

FIG. 8 is a block diagram of remote users and remote user connectionsaccording to an embodiment of the present invention;

FIG. 9A is a block diagram of a terminal/user according to an embodimentof the present invention;

FIG. 9B is a block diagram of a terminal according to an embodiment ofthe present invention;

FIG. 9C is a block diagram of a protocol processor to an embodiment ofthe present invention;

FIG. 10 is a block diagram of a computer used in an embodiment of thepresent invention;

FIG. 11 is a flow diagram of a method according to an embodiment of thepresent invention;

FIG. 12 is a table of configuration states according to an embodiment ofthe present invention;

FIG. 13A is a flow diagram of a method according to an embodiment of thepresent invention;

FIG. 13B is a flow diagram of a method according to another embodimentof the present invention;

FIG. 14 is a flow diagram of a method according to another embodiment ofthe present invention;

FIG. 15 is a flow diagram of a method according to another embodiment ofthe present invention;

FIG. 16 is a block diagram of a background communication system;

FIG. 17A is a block diagram of a background teleport;

FIG. 17B is a block diagram of another background teleport; and

FIG. 18 is a flow diagram of a background method of managing acommunication system.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

Referring now to the drawings, wherein like reference numerals designateidentical or corresponding parts throughout the several views, FIG. 1shows an example of a satellite communication system including sharedindependently administered satellite communication networks according toan embodiment of the present invention. In particular, FIG. 1 shows anexample of two shared independently administered satellite communicationnetworks, network A 122 and network B 124. Further, it should be notedthat although the description herein includes examples of satellitecommunication networks, the inventions also pertains to and includescommunication networks that do not include satellites.

Network A 122 includes network A upstream users 102 and network Aoperator 104 connected by IP network 110 to a shared multiport 100.Network A operator 104 provides management functions for network A, asdiscussed later in this specification. Further, network A 122 includessatellite X IF/RF converter 114 providing an IF connection to the sharedmultiport 100 and an RF connection to a satellite X 116 also formingpart of network A. The network connection between the satellite X IF/RFconverter 114 and satellite X 116 includes a satellite antenna and othersatellite related equipment (not shown). Further, network A 122 includesnetwork A remote users 118, which may include a plurality of remote usersites within a communication range of satellite X. Satellite X 116communicates with network A remote users using channel A 126. Network Aremote users 118 send and receive data with each other and with thenetwork A upstream users 102 via the aforementioned elements of networkA 122.

In addition, according to the example in FIG. 1, network B 124 includesnetwork B upstream users 106 and network B operator 108 connected by anIP network 111 to the shared multiport 100. Further, network B 124includes satellite X IF/RF converter 114 providing a connection betweenthe shared multiport 100 and the satellite X 116 also forming part ofnetwork B, via a satellite antenna (not shown). Further, network B 124includes network B remote users 120 that are within a communicationrange of satellite X 116 using channel B 128, and network B remote userscommunicate with each other and with the network B upstream users 106via the aforementioned elements of network B 124.

Thus, as can be seen in the example of FIG. 1, network A 122 and networkB 124 include independent (i.e., not shared) network A upstream users102 and network B upstream users 106, as well as independent remoteusers including network A remote users 118 and network B remote users120. However, network A 122 and network B 124 share a common sharedmultiport 100, satellite X IF/RF converter 114 and satellite X 116.Further, in the example of FIG. 1, each shared independentlyadministered network has an independent network operator (i.e., networkA operator 104 and network B operator 108) providing networkadministration functions, described later in the present specification.

Further, a satellite communication system according to the presentembodiment includes a hub network operator 112 that providesadministration functions for the entire satellite communication system,including network A and network B, and which also allocates resourcesamongst the shared independently administered networks, as describedlater in the specification.

In addition, although the present embodiment shows a single hub networkoperator 112, other embodiments according to the present inventioninclude a different number of hub network operators, to provide hubnetwork operator functionality at different physical locations, or toprovide visibility into network resources for a System Network Provider(SNP), for example, as discussed below in conjunction with the detaileddescription of the network management system embodiments.

Upstream users, like network A upstream user 102 in the embodiment ofFIG. 1, may be any network user providing business services to therespective remote users of that network. Further, remote users may beany network user that uses network services provided by the networkupstream user, or by other remote users. For example, a network upstreamuser may be a corporate headquarters, and field offices plus employeeworkstations at field offices may be examples of remote users.Alternatively, the network upstream user may represent a connection toanother network, for example the global internet, and remote users maybe any internet user on that internet connection. Other network upstreamusers may include, for example, fixed upstream headquarters with remotemobile platforms or remote sensors as remote users.

FIG. 2 includes an example of a further possible embodiment of thepresent invention including three shared independently administerednetworks A, B, and C (not individually labeled). As in the embodiment ofFIG. 1, networks A and B are configured to share the shared multiport100, the satellite X IF/RF converter 116, and satellite X 116. However,in the present embodiment, an additional network, network C also sharesthe shared multiport 100, and the shared multiport 100 providesconnections to a second satellite IF/RF converter, satellite X IF/RFconverter 214. Thus, network C includes network C upstream user 202, andnetwork C operator 204 connected through respective IP networks 110 tothe shared multiport 100. Further, network C includes satellite Y IF/RFconverter 214 that provides a connection between the shared multiport100 and satellite Y 216. Further, network C includes network C remoteusers 218 that are in communication with satellite Y 216 on channel C230. Network C remote users 218 use the shared and dedicated networkequipment to communicate amongst themselves and with network C upstreamusers 202.

Thus, as in the embodiment of FIG. 1, each shared independentlyadministered communication network in the embodiment of FIG. 2 includesindependent users, which may have independent IP spaces. In other words,none of network A upstream user 102, network B upstream user 106,network C upstream user 202, network A remote users 118, network Bremote users 120, and network C remote users 218 are shared between morethan one network (i.e., each user operates with a single network).However, each shared network shares the shared multiport 100, and in thepresent embodiment, the shared multiport 100 provides a connection tomore than one satellite IF/RF converter, satellite X IF/RF converter 114and satellite Y IF/RF converter 214. Further, network A and network Bshare satellite X IF/RF converter 114 and satellite X 116, while networkC includes satellite Y IF/RF converter 214 and satellite Y 216.

Further, in the example of FIG. 2, each shared independentlyadministered network has an independent network operator that isimplemented using a client/server architecture, and in the presentembodiment, three networks A, B, and C are implemented, each having aseparate network operator. Thus, network A operator is implemented asnetwork A operator client 204 and network A operator server 134, networkB operator is implemented as network B operator client 206 and network Boperator server 136, network C operator is implemented as network Coperator client 208 and network C operator server 238. Further, each ofthe networks are connected using separate IP networks, IP network A 110,IP network B 111, and IP network C 113. Further, a satellitecommunication system according to the present embodiment includes a hubnetwork operator 212 that provides administration functions for theentire satellite communication system, including networks A, B, and C,and which also allocates resources amongst the shared independentlyadministered networks A, B, and C.

Thus, according to the present invention, a single shared multiport mayprovide network connections to a plurality of satellite IF/RF convertersand satellites as part of a satellite communications system including aplurality of shared independently administered networks. In addition, aplurality of shared independently administered communication networksmay share the shared multiport 100.

In addition, although it was not specifically indicated above, thepresent embodiment includes various satellites operating in variousfrequency ranges. For example, each of satellite X and satellite Y mayinclude a Ku band satellite, a Ka band satellite, or a C band satellite.Further, there is no restriction on the types of satellites that mayoperate from a single shared multiport.

Although FIGS. 1 and 2 show independent IP networks 1 10 providingconnections between each upstream network user/network operator and theshared multiport 100, the present invention also includes sharing IPnetworks 110 between two or more networks, for example as shown in FIG.3.

FIG. 3 shows a further embodiment of a satellite communication systemincluding shared independently administered communication networks A andB, configured as in FIG. 1. In addition, each of the upstream users andnetwork managers share a single IP network, shared IP network 317.Further, though each network includes a separate network operator clientapplication in the present embodiment (i.e., network A operator client304 and network B operator client 308), they share a common networkoperator server 340.

FIG. 4 shows a possible embodiment of a shared multiport 100 accordingto the present invention, configured for use in a satellitecommunication system as shown in the embodiment of FIG. 3. Sharedmultiport 100 includes a shared hub modem chassis 300 and protocolprocessor A 302. In the present embodiment, protocol processor A 302provides network services for a single shared IP network, IP network117. Alternatively, a protocol processor may provide network servicesfor plural shared independently administered networks, e.g., networks Aand B. Thus, in that embodiment, protocol processor A 302 is shared bynetworks A and B.

In particular, each protocol processor provides network services such asdynamic assignment of available inroute bandwidth (e.g., based on afairness algorithm), IP routing to all line cards (described below),Internet Group Management Protocol (IGMP) based IP multicast support,hub side control for Transmission Control Protocol (TCP) and WebAcceleration to optimize TCP and web browsing over a satellite link,automatic adjustment of transmit power to maintain a low Bit Error Rate(BER) through the satellite link, downstream CIR, QoS and trafficprioritization, firewall functions (e.g., using Access Control Lists(ACL)), and link encryption to all or selected sites (e.g., using TripleData Encryption Standard (3DES)), for example.

The shared hub modem chassis 300 shown in FIG. 4 provides a connectionbetween each of the networks using the protocol processor and thecorresponding satellite IF/RF converter. Thus, when part of a systemconfigured according to the embodiment of FIG. 1, the shared hub modemchassis 300 provides a connection between protocol processor A 302 andthe satellite X IF/RF converter, and between protocol processor B 304and the satellite X IF/RF converter. Thus the shared hub modem chassis300 is shared by networks A and B.

Although FIG. 4 shows a protocol processor connected to a single sharedIP network, a protocol processor may be connected to plural networks,according to further embodiments of the present invention, for exampleas shown in FIGS. 5A-5C.

FIG. 5A shows a further embodiment of a shared multiport 100, accordingto an embodiment of the present invention. The shared multiport 100 ofthe present embodiment includes the shared hub modem chassis 300, theprotocol processor A 302 and a protocol processor BC 304. Protocolprocessor A 302 is dedicated to shared network A and provides networkservices for shared network A. Protocol processor BC 304 is sharedbetween network B and a third network C, and provides network servicesfor networks B and C. Further, in the present embodiment, the shared hubmodem chassis provides a connection to three satellite IF/RF converters,satellite X IF/RF converter providing satellite connections for networkA, satellite Y IF/RF converter providing satellite connections fornetwork B, and satellite Z IF/RF converter providing network connectionsfor network C. Accordingly, in the present embodiment, the shared hubmodem chassis 300 is shared by network A, network B, and network C.

FIGS. 5B and 5C show further alternative embodiments of coupling ashared hub modem chassis to a plurality of protocol processors, using anetwork switch 502, as in FIG. 5B or network hubs 504, as in FIG. 5C.

The protocol processor of the present invention supports a scalablesystem architecture. As additional users are added to the system, thereis additional burden added to the protocol processor. One or moreadditional protocol processors can be added to the system to providesupport for additional users without requiring a change to the otherparts of the system. Thus, a system can be initially created to supporta small number of users with a relatively small capital investment.Then, as the number of users increases, the system can be seamlesslyexpanded by adding additional protocol processors. In particular, when apredetermined usage threshold is reached, an additional protocolprocessor is added to the system. A communication processing load isautomatically redistributed from the first protocol processor to thefirst and second protocol processors. Further, as discussed above,additional user networks can be added to the system using a singleprotocol processor, or additional protocol processors can be added. Thesystem automatically redistributes the communication load over theavailable protocol processors. The predetermined threshold may bedetermined based upon a system status criteria, for example a networkmanagement system status report or a CPU utilization.

FIG. 6 shows a possible embodiment of shared hub modem chassis 300,according to an embodiment of the present invention and configured foruse in a shared multiport as in the embodiment of FIG. 5. Shared hubmodem chassis 300 includes three modem groups 602 providing connectionsbetween protocol processors and satellite IF/RF converters. In thepresent example, a first modem group 602 provides a connection betweenprotocol processor A and a satellite X IF/RF converter, a second modemgroup 602 provides a connection between protocol processor B and asatellite Y IF/RF converter, and a third modem group 602 provides aconnection between protocol processor B and a satellite Z IF/RFconverter. Thus, the modem group 602 provides an interface betweenbaseband frequency communications at the protocol processor and passbandfrequency communications suitable for a satellite IF/RF converter, andaccording to the present embodiment, each modem group is dedicated toone satellite IF/RF converter. Additionally, each modem group has acommon frame time reference (i.e., synchronizing pulse for the start ofeach multiplexed time frame), which may be different from the commonframe time reference of other modem groups. The common frame timereference implements a standard satellite communication protocol, forexample as described in Pritchard, Wilbur L., and Joseph A. Scivlli,Satellite Communication Systems Engineering, Prentice-Hall, 1986, whichis incorporated in its entirely herein by reference. Further, oneprotocol processor may make a connection to more than one modem groupaccording to the present invention. In addition, although the modemgroups 602 are represented with a same label, at least one modem group602 may be differently configured or include a different embodiment ofthe modem group 602 than the other modem groups 602 (e.g., differenttypes or numbers or configurations of line cards in one or each modemgroup 602).

Although the shared hub modem chassis embodiment in FIG. 6 includesthree modem groups, other embodiments of the shared hub modem chassisare possible having a different number of modem groups. Further, sinceeach modem group provides a connection between at least one protocolprocessor and a satellite IF/RF converter connected to a satellite,other embodiments of the shared hub modem chassis are possible havingconnections to other numbers of satellite IF/RF converters connected tosatellites. Thus, it is possible to increase or decrease the number ofsatellite IF/RF converters and satellites sharing a shared hub modemchassis by adding or removing, respectively, modem groups from theshared hub modem chassis.

FIG. 7 shows an embodiment of a modem group 602 according to anembodiment of the present invention. The modem group 602 includes amodulator line card 702 providing a connection between a protocolprocessor and a TX IF Cable 608 connected to a satellite transmitter(not shown) in a satellite IF/RF converter. Additionally, each line cardin a modem group shares a common frame time reference. A modulator linecard accepts packets from a protocol processor (e.g., using IP overEthernet), converts them to a serial stream (e.g., delimited HDLCframes), converts data to modulated symbols (e.g., QPSK) through amapping process and upconverts the symbols to IF. A demodulator linecard performs similar functions in a reverse order. The modem group 602of the present embodiment also includes four demodulator line cards 704connected to a splitter 606. The splitter 606 is also connected to an RXIF Cable 610 connected to a satellite receiver (not shown) in asatellite IF/RF converter. The splitter 606 receives satellitecommunications from the satellite IF/RF converter and distributes themultiplexed data in the satellite communications for use by theindividual demodulator line cards 704. The demodulator line cards 704demodulate the received communication data and provide that data to theprotocol processor.

Each demodulator line card 704 provides a communication demodulationcapability for remote users operating at a particular data rate. Thus,demodulation capability can be expanded or reduced by adding orremoving, respectively, demodulator line cards from a modem group.

Although the embodiment of FIG. 7 shows a modem group connected to asingle protocol processor, the modem group may also be connected to aplurality of protocol processors. Further, other modem group embodimentsare possible including a number of demodulator line cards 704 other thanshown here. In addition, although modulator line card 702 is differentlydesignated than each demodulator line card 704, a modem group embodimentincluding modulator/demodulator line cards that perform the functions ofboth modulator line card 702 and demodulator line card 704 are possible.Thus, each line card includes the ability to both transmit a downstreamcarrier and receive an upstream carrier. Further, although splitter 606is represented as being separate from the demodulator line cards 704, itis possible for the function performed by the splitter 606 to beimplemented within each demodulator line card, and therefore sharedbetween the demodulator line cards 704.

FIG. 8 shows a possible embodiment of network A remote users 118including two remote terminals/users 800 and three terminals 802 incommunication with satellite A 116. Other quantities of terminals 802and terminals/users 800 are also possible. Each terminal 802 includes asatellite antenna, and satellite IF/RF conversion functions, for exampleas in a Very Small Aperature Terminal (VSAT). Each user computerprovides communication capabilities appropriate to the type ofcommunication employed by the network (e.g., keyboard and terminal, orsensor and telemetry device). Further, the remote users 118 may includeone or more remote site/users 800 that include all the features ofterminal 802 and user computer 806.

Network A remote users 118 according to this embodiment also include aplurality of user computers 806 connected via communication connectionsto associated terminals 802. For example, a user computer 806 maycommunicate with a terminal 802 using a dedicated communication link804, which provides a special purpose point-to-point line between theterminal 802 and a user computer 806. Examples of a dedicatedcommunication link 804 include a RS-232 data link or other point topoint communication links. Alternatively, a plurality of user computers806 may communicate with network A via a single terminal 802 using amultidrop communication link 808. Multidrop communication link 808 mayinclude, for example, an RS-422 data link or an Ethernet data link.Further, a plurality of user computers 806 may communicate with networkA via a single terminal 802 using a wireless communication link 810. Awireless communication link 810 may be implemented using a radionetwork, like WiFi or WiMax, an optical network, microwave links, orother wireless communication links.

This arrangement of remote users advantageously allows one or aplurality of user computers to connect to a shared independently managednetwork using a remote site, and further allows those user computers tobe advantageously remotely located from the remote site. For example,with a WiMax wireless communication link, a plurality of user computerscan share a common VSAT terminal 802 within a region of a fewkilometers.

FIGS. 9A and 9B include detailed block diagrams of a possible embodimentof a remote site terminal/user 800 and single terminal 802 according tothe present invention. Each single terminal 802 includes a satellitemodem 902, a remote virtual router 904 and a remote virtual router tagtable 908. Each terminal/user 800 includes a satellite modem 902, aremote virtual router 904, a remote virtual router tag table 908 anduser interface 906. The remote virtual router 904 and remote virtualrouter tag table 908 work with the upstream virtual router 910 andupstream virtual router tag table 914 (described below) in conjunctionwith the shared network equipment, to provide a virtual routercapability.

As discussed above, each remote terminal transmits communications fromremote users to upstream users using the shared network equipment andeach remote terminal receives communications from upstream users sentvia the shared network equipment. The remote virtual router 904 appendsa virtual router tag (not shown) based on the contents of the remotevirtual router tag table 908 to each communication packet that isintended to be transmitted to an upstream user. The virtual router tagincludes a unique identifier that is mapped to a local IP address of aremote user or an upstream user, and the mapping between the virtualrouter tag and each local IP address is stored in the remote virtualrouter tag table 908. A duplicate copy of the mapping is also stored inthe upstream virtual router tag table 914 (discussed below). Further,the remote virtual router removes a virtual router tag from eachcommunication packet transmitted to a remote user and routes the packetto the local IP address of a remote user, based on the contents of theremote virtual router tag table 908.

FIG. 9C is a detailed block diagram of protocol processor 302, whichincludes upstream virtual router 910 operatively connected to upstreamvirtual router tag table 914 and protocol converter 912. The protocolconverter 912 converts communications from line cards in the shared hubmodem chassis for transmission to a client on the IP network andconverts communications from a client on the IP network for transmissionto a line card in the shared hub modem chassis. The upstream virtualrouter 910 appends a virtual router tag (not shown) based on thecontents of the upstream virtual router tag table 914 to eachcommunication packet that is intended to be transmitted to a remote useron a particular VLAN. The virtual router tag includes a uniqueidentifier that is mapped to a local IP address of a remote user or anupstream user, and the mapping between the virtual router tag and eachlocal IP address is stored in the upstream virtual router tag table 914.Further, the upstream virtual router 910 removes a virtual router tagfrom each packet to be transmitted to an upstream user and routes thepacket to the local IP address of the upstream user based on thecontents of the upstream virtual router tag table 914.

Thus, communications between the protocol processor and a remoteterminal according to an embodiment of the present invention includes avirtual router capability that repackages IP packets into virtual routerpackets by adding a virtual router tag. Each intermediate systemelement, including the shared hub modem chassis, satellite IF/RFconverter and satellite, is configured to pass the virtual routerpackets along. At the protocol processor end, virtual router packets areconverted back to IP packets by consulting a virtual router lookup tablethat maps the combined virtual router address and IP address back intoan IP address. Similarly, at the remote end, downstream virtual routerpackets are converted back to IP packets using the virtual router table.

This arrangement allows complete freedom in the administration ofnetworks that share hardware. Thus, a first shared network operator mayselect and assign IP addresses for first shared network users withoutregard to or knowledge of any IP addresses selected by a second networkoperator for second network users. For example, network operator A mayassign a network A remote user the IP address 10.0.0.1 and networkoperator B may also assign a network B remote user the same IP address,10.0.0.1, without any risk of conflict.

Further, a capability of a communication system can be flexibly variedat least by 1) changing a number of modem groups, 2) changing a numberof enabled line cards, 3) changing a number of communicating satellites,or 4) changing a number of protocol processors. In particular, thesystem may be created with a relatively small capital investment, butmay be expanded without adding a new hub modem chassis.

First, the system communication capability may be changed by changing anumber of modem groups. As discussed above, each modem group provides apotentially unique independently administered network capability to thecommunication system. Each network may be differently configured tosatisfy different technical or business purposes. For example, eachnetwork may support a different encryption scheme (e.g., havingdifferent encryption levels on one network than on other networks in thecommunication system), different communication purposes (e.g., voicepriority communication on one network and data priority communication onanother network in the communication system), different QoS scheme(e.g., different QoS levels on one network than on other networks in thecommunication system), different bandwidth allocation schemes anddifferent owners or system administrators on each network. A number ofmodem groups may be reduced by reallocating line cards of an existingmodem group to one or more other modem groups in the hub modem chassis.Alternatively, a modem group may be added to the system by reallocatingline cards of existing modem groups or by adding new line cards andallocating them to a new modem group. Thus, additional independentlyadministered networks may be added to the communication system withoutadding an additional hub modem chassis.

Second, a total upstream communication bandwidth of a particular modemgroup may be changed by allocating additional line cards to that modemgroup, or by de-allocating line cards. For example, when the desiredbandwidth exceeds a predetermined threshold, one or more additional linecards are enabled for a modem group and communications are redistributedover all the line cards in the enlarged modem group to allow thecommunication system to provide increased bandwidth without adding anadditional hub modem chassis. The predetermined threshold may bedetermined based upon a system status criteria, for example a networkmanagement system status report or a CPU utilization.

Third, the communication system may be expanded to support new users orto allocate communication resources to a particular group of existingusers. For example, the communication system may be expanded to supportnew users in a new geographic region by adding an additional satellitecapability including a communication link to an additional satellite.The additional satellite capability is added to the existing system byadding or allocating one or more new modem groups in the shared hubmodem chassis and connecting the new modem group to an additionalsatellite via an IF/RF converter, as discussed above. Thus, a newsatellite capability allowing communication with a new group of usersusing an additional satellite is easily added to the communicationsystem without adding an additional hub modem chassis.

Fourth, a communication capability of the communication system may beexpanded to include additional protocol processing capability by addingadditional protocol processors. For example, if a desired level ofprotocol processing capability increases beyond a particular threshold,additional protocol processors may be enabled, and the protocolprocessing capability is shared between plural protocol processors. Forexample, an increase in voice communication capacity requires anincreased protocol processing. Thus, if a desired a voice communicationcapacity exceeds a predetermined threshold, an additional protocolprocessor may be enabled to increase the protocol processing capabilityof the communication system.

FIG. 10 illustrates a computer system 1001 upon which an embodiment ofthe present invention may be implemented. The computer system 1001includes a bus 1002 or other communication mechanism for communicatinginformation, and a processor 1003 coupled with the bus 1002 forprocessing the information. The computer system 1001 also includes amain memory 1004, such as a random access memory (RAM) or other dynamicstorage device (e.g., dynamic RAM (DRAM), static RAM (SRAM), andsynchronous DRAM (SDRAM)), coupled to the bus 1002 for storinginformation and instructions to be executed by processor 1003. Inaddition, the main memory 1004 may be used for storing temporaryvariables or other intermediate information during the execution ofinstructions by the processor 1003. The computer system 1001 furtherincludes a read only memory (ROM) 1005 or other static storage device(e.g., programmable ROM (PROM), erasable PROM (EPROM), and electricallyerasable PROM (EEPROM)) coupled to the bus 1002 for storing staticinformation and instructions for the processor 1003.

The computer system 1001 also includes a disk controller 1006 coupled tothe bus 1002 to control one or more storage devices for storinginformation and instructions, such as a magnetic hard disk 1007, and aremovable media drive 1008 (e.g., floppy disk drive, read-only compactdisc drive, read/write compact disc drive, compact disc jukebox, tapedrive, flash memory drive, and removable magneto-optical drive). Thestorage devices may be added to the computer system 1001 using anappropriate device interface (e.g., small computer system interface(SCSI), integrated device electronics (IDE), enhanced-IDE (E-IDE),direct memory access (DMA), or ultra-DMA).

The computer system 1001 may also include special purpose logic devices(e.g., application specific integrated circuits (ASICs)) or configurablelogic devices (e.g., simple programmable logic devices (SPLDs), complexprogrammable logic devices (CPLDs), and field programmable gate arrays(FPGAs)).

The computer system 1001 may also include a display controller 1009coupled to the bus 1002 to control a display 1010, such as a cathode raytube (CRT), for displaying information to a computer user. The computersystem includes input devices, such as a keyboard 1011 and a pointingdevice 1012, for interacting with a computer user and providinginformation to the processor 1003. The pointing device 1012, forexample, may be a mouse, a trackball, or a pointing stick forcommunicating direction information and command selections to theprocessor 1003 and for controlling cursor movement on the display 1010.In addition, a printer may provide printed listings of data storedand/or generated by the computer system 1001.

The computer system 1001 performs a portion or all of the processingsteps of the invention in response to the processor 1003 executing oneor more sequences of one or more instructions contained in a memory,such as the main memory 1004. Such instructions may be read into themain memory 1004 from another computer readable medium, such as a harddisk 1007 or a removable media drive 1008. One or more processors in amulti-processing arrangement may also be employed to execute thesequences of instructions contained in main memory 1004. In alternativeembodiments, hard-wired circuitry may be used in place of or incombination with software instructions. Thus, embodiments are notlimited to any specific combination of hardware circuitry and software.

As stated above, the computer system 1001 includes at least one computerreadable medium or memory for holding instructions programmed accordingto the teachings of the invention and for containing data structures,tables, records, or other data described herein. Examples of computerreadable media are compact discs, hard disks, floppy disks, tape,magneto-optical disks, PROMs (EPROM, EEPROM, flash EPROM), DRAM, SRAM,SDRAM, or any other magnetic medium, compact discs (e.g., CD-ROM), orany other optical medium, punch cards, paper tape, or other physicalmedium with patterns of holes, a carrier wave (described below), or anyother medium from which a computer can read.

Stored on any one or on a combination of computer readable media, thepresent invention includes software for controlling the computer system1001, for driving a device or devices for implementing the invention,and for enabling the computer system 1001 to interact with a human user(e.g., print production personnel). Such software may include, but isnot limited to, device drivers, operating systems, development tools,and applications software. Such computer readable media further includesthe computer program product of the present invention for performing allor a portion (e.g., locally portion of distributed processing) of theprocessing performed in implementing the invention.

The computer code devices of the present invention may be anyinterpretable or executable code mechanism, including but not limited toscripts, interpretable programs, dynamic link libraries (DLLs), Javaclasses, and complete executable programs. Moreover, parts of theprocessing of the present invention may be distributed or centralizedfor better performance, reliability, and/or cost.

The term “computer readable medium” as used herein refers to any mediumthat participates in providing instructions to the processor 1003 forexecution. A computer readable medium may take many forms, including butnot limited to, non-volatile media, volatile media, and transmissionmedia. Non-volatile media includes, for example, optical, magneticdisks, flash memory, and magneto-optical disks, such as the hard disk1007 or the removable media drive 1008. Volatile media includes dynamicmemory, such as the main memory 1004. Transmission media includescoaxial cables, copper wire and fiber optics, including the wires thatmake up the bus 1002. Transmission media also may also take the form ofacoustic or light waves, such as those generated during radio wave andinfrared data communications.

Various forms of computer readable media may be involved in carrying outone or more sequences of one or more instructions to processor 1003 forexecution. For example, the instructions may initially be carried on amagnetic disk of a remote computer. The remote computer can load theinstructions for implementing all or a portion of the present inventionremotely into a dynamic memory and send the instructions over atelephone line using a modem. A modem local to the computer system 1001may receive the data on the telephone line and use an infraredtransmitter to convert the data to an infrared signal. An infrareddetector coupled to the bus 1002 can receive the data carried in theinfrared signal and place the data on the bus 1002. The bus 1002 carriesthe data to the main memory 1004, from which the processor 1003retrieves and executes the instructions. The instructions received bythe main memory 1004 may optionally be stored on storage device 1007 or1008 either before or after execution by processor 1003.

The computer system 1001 also includes a communication interface 1013coupled to the bus 1002. The communication interface 1013 provides atwo-way data communication coupling to a network link 1014 that isconnected to, for example, a local area network (LAN) 1015, or toanother communications network 1016 such as the Internet. For example,the communication interface 1013 may be a network interface card toattach to any packet switched LAN. As another example, the communicationinterface 1013 may be an asymmetrical digital subscriber line (ADSL)card, an integrated services digital network (ISDN) card or a modem toprovide a data communication connection to a corresponding type ofcommunications line. Wireless links may also be implemented. In any suchimplementation, the communication interface 1013 sends and receiveselectrical, electromagnetic or optical signals that carry digital datastreams representing various types of information.

The network link 1014 typically provides data communication through oneor more networks to other data devices. For example, the network link1014 may provide a connection to another computer through a localnetwork 1015 (e.g., a LAN) or through equipment operated by a serviceprovider, which provides communication services through a communicationsnetwork 1016. The local network 1014 and the communications network 1016use, for example, electrical, electromagnetic, or optical signals thatcarry digital data streams, and the associated physical layer (e.g., CAT5 cable, coaxial cable, optical fiber, etc). The signals through thevarious networks and the signals on the network link 1014 and throughthe communication interface 1013, which carry the digital data to andfrom the computer system 1001 maybe implemented in baseband signals, orcarrier wave based signals. The baseband signals convey the digital dataas unmodulated electrical pulses that are descriptive of a stream ofdigital data bits, where the term “bits” is to be construed broadly tomean symbol, where each symbol conveys at least one or more informationbits. The digital data may also be used to modulate a carrier wave, suchas with amplitude, phase and/or frequency shift keyed signals that arepropagated over a conductive media, or transmitted as electromagneticwaves through a propagation medium. Thus, the digital data may be sentas unmodulated baseband data through a “wired” communication channeland/or sent within a predetermined frequency band, different thanbaseband, by modulating a carrier wave. The computer system 1001 cantransmit and receive data, including program code, through thenetwork(s) 1015 and 1016, the network link 1014 and the communicationinterface 1013. Moreover, the network link 1014 may provide a connectionthrough a LAN 1015 to a mobile device 1017 such as a personal digitalassistant (PDA) laptop computer, or cellular telephone.

Each network operator includes a network management system (NMS) thatprovides network administration functionality with visibility into alevel of network resources that may be differently configured. Networkresources managed by the NMS include all configurable aspects of thecommunication system including remote user equipment, line cards, theshared hub modem chassis, and the protocol processors, for example. TheNMS includes a database that stores configuration parameters andprivileges for each resource in the communication system.

Each NMS may be configured as a client/server application with a clientNMS application and a server NMS application. The client and server NMSapplications may execute on a same computer or on different computerslocated in a same location or at different locations. Although the NMSserver application may receive communication for each of the sharednetworks configured to share common hardware, as in the embodiment ofFIG. 3, the NMS server application is configured to only provide networkmonitoring and status information to an NMS client regarding networksover which the NMS client has administrative privileges. Theconfiguration of the NMS client may be based on a content of a database.Further, the NMS server only allows an NMS client to perform networkmanagement functions that the NMS client is privileged to perform basedon the database content. In addition, the NMS server only allows an NMSclient to manage the user accounts of users on a network that the NMSclient is privileged to administer, based on the database content.

For each configurable resource in the communication system, the NMSstores a metadata value including a state variable representing a stateof a change to the associated parameter, an original value of theconfiguration parameter, and a desired changed value of theconfiguration parameter. The NMS uses the stored metadata to coordinatea change in configuration of the communication system with minimaldisruption to communication system operation. For example, one or morenetwork configuration changes may be planned using the NMS, and thedesired changed value of each configuration parameter is stored in themetadata. Then, NMS can be scheduled to make all the networkconfiguration parameters at the same time, and at a time that is mostconvenient for users, for example at night time when communicationsystem usage is low.

To implement a network configuration change, the NMS uses a coordinatedthree state change mechanism. In particular, in step 1, desired changesare entered in the metadata stored in the configuration database. Instep 2, the NMS displays the desired changes and allows a networkoperator to make further changes, and in step 3 the NMS communicates thechanges to the participating network resources, monitors their responseand stores their status in the database metadata.

This three-step change process gives the network operator ultimatecontrol over operational network components, because no change takesplace without the operator initiating it. However, the three-step changeprocess also creates a situation where the NMS database is temporarilyout-of-sync with the actual network (i.e., after the operator has madedatabase modifications, but before they have been applied to thenetwork). Accordingly, to help operators easily manage this situationand others like it, each key component of the network maintains andreports a configuration state variable that shows the current status ofthat key component.

FIG. 11 shows an example of a method of changing a networkconfiguration, according to an embodiment of the present invention. Instep S1102, a remote user is already configured, commissioned, and allprevious changes have been applied, thus the remote user reports itsconfiguration state as “Nominal” and the configuration state ismonitored and displayed for the network operator and stored in the NMSmetadata. In step S1104, a user makes some change to the configurationdatabase, for example, the user changes a QoS parameter. In step S1106,all users are informed of possible changes to Upstream QoS caused by theconfiguration database changes made in S1104. In step S1108, each userreviews the pending configuration changes and resulting changes to QoS.In step S1114, the users indicate if pending changes are desired. If thechanges are desired, proceed to step S110 in which the changes areapplied to the data path elements (e.g., shared multiport, satelliteIF/RF converters, remote users, etc . . .). If the changes are notdesired, proceed to step S1112, in which the user that changed theconfiguration database removes that change from the database.

Thus, according to the present invention, the configuration statevariable is associated with each configurable element of thecommunication system and the configuration state value can be easilymanaged by the NMS thereby allowing configuration changes to be made inan orderly, predictable, and controlled manner.

In a further example of a method of making a configuration change, a hubfrequency change is desired. Using the NMS, a network operator entersthe desired hub frequency change and the NMS stores the hub frequencychange in the metadata database. Further, the NMS makes all otherrelated changes to configurable communication system equipment,including changes to the frequency of each remote user operating withthat hub. At this point the network operator can review all changesrelated to the hub frequency change, including an indication of whichparameters must consequently change on each related piece ofcommunication equipment, prior to applying that change, and ifnecessary, the network operator can modify or abort the change.

Further, as a network operator enters configuration parameters into theNMS, the NMS displays an indication of which further configurationparameters may also be required and indicates if the configurationparameters have been fully entered.

Further, when making a configuration change, the NMS will periodicallypoll related communication system elements to determine their currentconfiguration state.

Each configurable element of the communication system has acommunication state, which according to one embodiment of the presentinvention, includes the configuration states as shown in FIG. 12.

The network management system 804 may be configured to perform a hubnetwork operator function or a virtual network operator function. If thenetwork management system is configured to perform the role of a hubnetwork operator, the network operator 800 is configured for huboperator use, as in hub network operator client 112 and hub networkoperator server 140 of FIG. 1. If the network management system 804 isconfigured to perform the role of a virtual network operator, thenetwork operator 800 is configured for network operator use, as in thenetwork A operator client 104 and network A operator server 134, or asin network B operator client 108 and network B operator server 136 ofFIG. 1. Further, the network management system is configured to providedifferent levels of capability for different users.

For example, one possible embodiment of the network management system(NMS) 804, provides different levels of permission and visibility tonetwork resources depending upon the type of user. For example, a hubnetwork operator user type identified as a Hub Network Operator (HNO)Super User has permission and visibility to all communication systemresources, a network operator user type identified as a Virtual NetworkOperator (VNO) Super User has visibility only to resources of one sharedindependently administered network in the communication system, and anetwork operator user type identified as a VNO Guest User has read-onlypermission to observe configuration parameters and network status forone shared independently administered network in the communicationsystem. The network management system 804 also includes the ability tocreate other user types with other permissions and visibility of networkresources. Further, VNO accounts may be configured to provide access tothe resources allocated to the VNO's network and may be configured tonot have access to the resources allocated to other networks in theshared satellite communication system. Alternatively, remote users andcommunications in a network may be made part of different networksubgroups, and different VNOs on the same network may be configured tohave access to remote users and communications in one subgroup and maybe further configured not to have access to remote users andcommunications in another subgroup.

VNO accounts are configured for each VNO NMS user and include userinformation, for example name/password, user type (e.g., VNO Super Useror VNO Guest). VNO Super Users may use the network management system 804to perform virtual network operations, for example to add, modify anddelete network remote users, activate and deactivate network remoteusers, select Quality of Service (QoS) profiles, monitor and queryremote statistics, and have visibility only to their independent sharednetwork. VNO Super Users cannot add or modify carriers, independentlyadd or modify line cards or protocol processors, independently add ormodify hardware components, or view other shared networks in thecommunication system, because these features are reserved to HNO andSystem Network Provider (SNP) accounts due to their impact on shared RFconfigurations.

Participants in a method of operating a satellite communication systemthat includes shared independently administered satellite communicationnetworks include a Host Network Operator, a Virtual Network Operator, aShared Network Provider, and Users. These participants achieve theirbusiness goals through the use of a shared communications system,according to the present invention.

A Host Network Operator (HNO) provides a hosting environment forsophisticated enterprise or service provider customers who desire morecontrol over the network management of their services. The HNO role maybe performed by companies who own or operate satellites to broadenexisting space segment distribution channels or to create new channelsfor service offerings. HNOs manage shared network equipment and allocatenetwork resources to Virtual Network Operators (VNOs). For example, HNOsperform network management, installation and maintenance services forVNOs.

Further, HNOs are responsible for purchasing and maintaining a portionof the hardware and software in a satellite network. In particular, HNOsare responsible for satellites and satellite ground equipment, includingspacecraft, transponders, hub antenna components, and hub RadioFrequency Transceivers (RFT) or radio frequency/intermediate frequencyconverters (IF/RF converters). HNOs are also responsible for a portionof the shared multiport equipment. At the shared multiport, HNOs areresponsible for the hub modem chassis, protocol processors, host NetworkManagement System (NMS) server, and host NMS clients.

HNOs are responsible for managing some system parameters, includinginbound and outbound carriers, bandwidth regions, carrier frequencies,power, bit rates, acquisition and uplink control parameters, andInternet Protocol (IP) addresses of hub modems, NMS clients and servers,protocol processors and upstream routers, for example.

HNOs provide services to VNOs, including remote commissioning support,link budget preparation, hub equipment maintenance, upstream internetconnection/private data connection maintenance, and coordination ofsoftware/firmware upgrades, for example. Further, HNOs have fullvisibility to all parts of the network using the NMS.

HNOs derive revenue from space segment operations, co-location services,and network management fees to VNOs. The network management feesinclude, for example, commissioning, configuration management, real-timemonitoring, and periodic report generation fees, for example.

A Virtual Network Operator (VNO) is a “non-facilities” based provider ofsatellite network operator services that will be supported by the HostNetwork Operator business model. The VNO manages an independentlymanaged, shared network and allocates network resources to users of thatnetwork. The VNO role is performed by sophisticated enterprise customersand service providers, and allows them to operate and managestate-of-the-art satellite networks. VNO is a low cost way of enteringinto a Satellite Network Operations business because much of the upfrontcapital investment has already been made, and VNOs can incrementallygrow system capability as business opportunities grow. Further, the VNObusiness model provides greater control over end user networks, therebyproviding better customer service.

VNOs are responsible for obtaining and maintaining a portion of thehardware and software in a satellite network, or VNOs contract thoseresponsibilities to the HNO. In particular, at the shared multiport,VNOs are responsible for line cards, netmodems, network user equipment,and virtual NMS client software. VNOs support line card installation(through coordination with HNO, if necessary), commissioning of newremote sites, and support of all network user sites. VNOs manage allnetwork user configuration, including rate shaping, network user IPaddress assignment (through coordination with HNO, if necessary),in-route timeplan and outroute frame configuration, Network AddressTranslation (NAT) and Dynamic Host Configuration Protocol (DHCP), forexample. Further, VNOs coordinate software/firmware upgrades with HNOand SNP.

VNOs derive revenue from recurring enterprise service fees, installationand maintenance of network user equipment and software, and as a spacesegment reseller, for example.

Each network user on an independently managed, shared network typicallyreceives service from a single VNO. For example, those services mayinclude web hosting, content or DNS caching, data or video broadcastservices, and other IP related services. Further, network users may alsoreceive support, for example, commissioning support, help desk andtechnical support (e.g., during an outage), and changes or additions toQoS profiles.

The Shared Network Provider (SNP) performs a variety of tasks, includingan initial survey of the shared multiport site, initial installation ofequipment at the shared multiport site, broadband network operationtraining to HNOs and VNOs, ongoing technical support and consultingservices to HNOs and VNOs, and software/firmware updates andmaintenance, for example. In addition, the SNP may have visibility toall parts of the network through the NMS, at the discretion of therelevant HNO. Further, the SNP provides technical expertise to HNOs, forexample including link budget and network architecture expertise.

Consulting services provided by the SNP include hub engineering design,initial network configuration, file server configuration and base bandhub station installation, for example. Broadband network operationtraining includes NMS training, Time Division Multiple Access (TDMA)System training, Network Operations Center (NOC) training, for example.SNP provided maintenance services include broadband routersoftware/firmware maintenance, NMS software maintenance, and protocolprocessor software/firmware maintenance, for example.

FIG. 13A shows a possible embodiment of a shared independentlyadministered business method of a communication system that includesshared independently administered networks, and in particular, a methodof adding a new shared network to an existing satellite communicationssystem. In step S1302 a HNO and VNO add a modem group to an existingshared multiport that is already connected via a satellite IF/RFconverter to an existing satellite. The HNO selects a number of linecards and upstream and downstream carrier rates for the modem group asappropriate for the service level desired for the new network to beadded. In step S1304 the HNO uses a hub network operator to allocateprivileges to a new network operator and adds the operator to thecommunication system. In S1306, the VNO of the new network adds newupstream and remote user sites to the new network configuration usingthe new network operator, and in S1308, the VNO configures the networkresources for operation according to the VNOs business goals. In S1310,the new network is administered, including system administrationfunctions performed by the HNO and SNP, and network administrationfunctions performed by the VNO. In step S1312, the new network isoperated, including system monitoring functions performed by the SNP,billing functions performed by the HNO and VNO and communicationfunctions performed by the users, for example.

FIG. 13B shows a further possible embodiment of a method of operating acommunication system including shared independently administeredcommunication networks, and in particular, an embodiment of a method toadd a satellite, satellite IF/RF converters, and a modem group to anexisting shared multiport to create a new shared network. Steps S1302through S1312 are performed similarly to the steps in the embodiment ofFIG. 13A. In step S1308 a new satellite and a new satellite IF/RFconverter are added to the communication system and in step S1310 theadded satellite IF/RF converter is connected to the new modem group inthe existing shared multiport.

Thus, the existing shared multiport is reconfigured, with the additionof the new modem group, to operate with an additional new satellite notpreviously connected, and it is not necessary to add a new hub modemchassis for connection to an additional satellite, as required bybackground methods.

FIG. 14 shows a possible embodiment of a method of configuring sharednetwork resources, as shown in step S1308 in the embodiments of FIGS.13A and 13B. In step S1402, global privileges (i.e., privileges to allresources in the communication system) are granted to a hub networkoperator by the SNP and the hub network operator is configured to havethose privileges. In step S1404, the hub network operator grants certainprivileges to observe and control network resources to each of thevirtual network operators in the communication system. As discussedabove, each virtual network operator is typically granted privileges toresources of its shared independently administered network. In stepS1406, the hub network operator administers resources throughout thecommunication system, setting up those resources for operation with ashared network. In step S1408, a first virtual network operatoradministers resources throughout the first network, setting up thoseresources for operation, including activating/deactivating users,setting up IP addresses, etc . . . , as discussed above. In step S1410,a second network operator administers resources throughout the secondnetwork, setting up those resources for operation. The first virtualnetwork operator does not have access to resources on the secondnetwork, and likewise, the second virtual network operator does not haveaccess to resources on the first network. A hub network operator hasaccess to all resources in the communication system, including firstnetwork resources and second network resources.

FIG. 15 shows an example of operating a shared network, as in step S1312in FIGS. 13A and 13B, according to a possible embodiment of the presentinvention. In step S1502 the SNP, HNO and VNOs perform system monitoringand maintenance functions including monitoring the health of systemequipment and preparing periodic software and firmware upgrades toelements of the communication system. In step S1504, the HNO and a firstvirtual network operator further monitor the status of the first networkto provide support to first network users. In step S1504, the HNO and asecond virtual network operator further monitor the status of the secondnetwork to provide support to second network users. The first virtualnetwork operator does not have access to users on the second network,and likewise, the second virtual network operator does not have accessto users on the first network. In step S1512, SNPs bill the HNO forprovided maintenance and monitoring services. In step S1514, the HNObills a first VNO for first network communication resources allocated tothe VNO and for usage of the first network as monitored by the HNO. Instep S1516, the HNO bills a second VNO for second network communicationresources allocated to the VNO and for usage of the second network asmonitored by the HNO. In step S1518, the first VNO bills users of thefirst network based on monitored usage, and in step S1520, the secondVNO bills users of the second network based on monitored usage.

Numerous modifications and variations of the present invention arepossible in light of the above teachings. It is therefore to beunderstood that within the scope of the appended claims, the inventionmay be practiced otherwise than as specifically described herein.

1. A method of sharing a satellite communication system having a commonequipment, comprising: billing a first user for sending a first messageusing the common equipment over a first satellite link; billing a seconduser for sending a second message using the common equipment over asecond satellite link, wherein said first satellite link is differentthan said second satellite link; billing a first network operator forbilling the first user; and billing a second network operator forbilling the second user.
 2. The method of claim 1, further comprising:allocating a first portion of the common equipment to the first networkoperator; and allocating a second portion of the common equipment to thesecond network operator.
 3. The method of claim 2, further comprising:allocating a third portion of the common equipment to the first user;and allocating a fourth portion of the common equipment to the seconduser.
 4. The method of claim 2, wherein the first portion of the commonequipment includes a first modem group in a hub modem chassis, and thesecond portion of the common equipment includes a second modem group inthe hub modem chassis.
 5. The method of claim 3, wherein the thirdportion of the common equipment includes a first quality of servicemechanism, and the fourth portion of the common equipment includes asecond quality of service mechanism.
 6. The method of claim 3, whereinthe third portion of the common equipment includes a first communicationbandwidth allocation mechanism, and the fourth portion of the commonequipment includes a second communication bandwidth allocationmechanism.
 7. The method of claim 4, wherein the third portion of thecommon equipment includes a portion of a total bandwidth of the firstmodem group and the fourth portion of the common equipment includes aportion of a total bandwidth of the second modem group.